Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
London Borough of Hillingdon

Plan timetable

There is a problem

  • 12 ‘plan’ fields do not match the ‘reference’ field in the plan dataset

entity: 5109971

reference
LP9-Consultation-proposed-LP-end
plan

undefined

LP-HILLINGDON-2026
plan-event
proposed-plan-consultation-end
event-date
2027-08-27
actual-date
entry-date
2026-05-28
notes

How to fix this issue

Your data is missing a plan.

The plan timetable guidance explains how to fix the issue:

plan

This is the unique reference for your overall plan. For example:

  • LP-BRX-2024
  • barnet-local-plan-2021-2036
  • hertfordshire-minerals-and-waste-plan
  • essex-minerals-plan
  • essex-waste-plan
  • county-durham-supplementary-plan

The ‘plan’ field in your plan timetable dataset must match the ‘reference’ field from your plan dataset.

This diagram shows the relationship between the plan dataset and the plan timetable dataset. The reference value from your plan dataset needs to match the plan value in your plan timetable dataset. This is so that we can match your timetable to the right plan.

How to improve London Borough of Hillingdon’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL